Porting user profiles between communication devices in an enterprise

ABSTRACT

In one embodiment, an enterprise network is provided that includes a mobility agent  150  associated with a switch/server  100  or  104 . The mobility agent creates a visitor application record  172  associated with a second communication device  140   b . The visitor application record is associated with a first subscriber. A second subscriber is normally associated with the second communication device, and the first subscriber with a first communication device  136   a . In response to creating the visitor application record, the native communication device record is associated with a virtual communication device having the same public and/or private numbers as the second communication device  140   b.

CROSS REFERENCE TO RELATED APPLICATION

This application is a divisional of U.S. Ser. No. 11/502,200, filed Aug.9, 2006, entitled “ENTERPRISE MOBILITY USER”, the disclosure of which isincorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The invention relates generally to telecommunications systems andparticularly to wired mobility in telecommunications systems.

BACKGROUND OF THE INVENTION

Enterprise user mobility, or the ability of subscribers to use stationslocated across the enterprise network while still being able to receiveconsistent phone service, is highly desirable in the global marketplace.Many large companies are commonly decentralized with large campuses andbranch offices located around the world. Preferably, enterprise usermobility provides subscribers with the continued access to features andother functionality located on the subscriber's home, or assigned,station.

Enterprise user mobility is currently being offered in Voice overInternet Protocol or VoIP products of various vendors, such as ExtensionMobility™ by Cisco. The Cisco product has an extensive ApplicationProgram Interface or API that allows access to third party applicationsto setup the home and visited, or remote, VoIP stations for remoteaccess without the subscriber needing to touch either handset. To effectthe reconfiguration of the remote station, the system administrator usesthe API to enter a User Identifier or UI and Personal IdentificationNumber or PIN. When the subscriber logs into the visited station and issuccessfully verified, the visited station automatically reconfigureswith the subscriber's home station profile information. Where more thanone switch is involved at the locations of the home and visited station,call processing is performed at the home switch and not the visitedswitch because the visited switch simply acts as a router.

These products, however, are limited to VoIP stations and are notadaptable to circuit-switched or Time Division Multiplexed or TDMtelephones. IP networks generally provide an excellent infrastructurefor geographically distributing components of a telecommunicationsystem. The underlying IP network is optimal for transmission forcontrol signaling, and, when bandwidth is available, can provide anacceptable Quality of Service (or QoS) or Grade of Service (or GOS) forvoice communications. However when insufficient network resources areavailable for voice communications or one or more IP network componentsare down, voice communications can be adversely impacted. While greatstrides have been made to provide improved levels of voice quality inVoIP communications, rapid and unexpected deteriorations in the QoS orGOS still occur with some frequency and are unacceptable for manybusinesses.

For this reason, many businesses prefer wired circuit-switched or TDMcommunication devices. Although intra-switch wired mobility, such ashoteling or hot-desking, is known, inter-switch enterprise user wiredmobility is not available for circuit-switched or TDM communicationdevices, particularly wired mobility in which the subscriber has closeto the full functionality that the subscriber would have if he or shewere at his or her home station. As will be appreciated, hoteling orhot-desking is a function that allows subscribers, without a nativestation, to be assigned anywhere in the local area network controlled bya common enterprise switch. Additionally, even with IP enabled mobilitythe native subscriber normally associated with the remote IP phone takenover by the traveling subscriber is no longer associated with that IPphone. This can create problems with the native subscriber having remoteaccess to the features of the IP phone, such as abbreviated dial,bridged appearance, dial intercom, and the like.

SUMMARY OF THE INVENTION

These and other needs are addressed by the various embodiments andconfigurations of the present invention. The present invention isdirected to subscriber mobility in a centralized or decentralizedenterprise network.

In a first embodiment, a method includes the steps of:

(a) providing a native communication device record for a secondcommunication device associated with a second subscriber;

(b) thereafter creating a visitor application record associated with thesecond communication device, the visitor application record beingassociated with a first subscriber different from the second subscriberand the first subscriber normally being associated with a firstcommunication device; and

(c) in response to step (b), associating the native communication devicerecord with a virtual communication device, the virtual communicationdevice having the same public and/or private numbers as the secondcommunication device.

While the first subscriber is associated with the second communicationdevice, a home communication device record is maintained for the firstcommunication device. The home communication device record configuresthe first communication device for the first subscriber. While the firstsubscriber is associated with the second communication device, a homeapplication record is maintained to redirect incoming calls for thefirst communication device to the second communication device.

The native communication device and visitor application records aremaintained independent of one another while the first subscriber isassociated with the second communication device. This permits the secondsubscriber to receive incoming calls to the second communication device,make calls remotely using, as call origination information, number ofthe second communication device, and access remotely features of thesecond communication device and the first subscriber to receive incomingcalls at, make outgoing calls from, and access first communicationdevice features from the second communication device. This permits thesecond subscriber to become a remote user of another enterprisecommunication device while his home communication device is in use bythe first subscriber. This implementation is thus fundamentallydifferent from logging out of an IP communication device and logginginto another IP device at a different geographical location but keepingthe home office as the IP station's gatekeeper.

The first embodiment may be used to provide intra- and inter-switch andpacket-switched and circuit-switched subscriber mobility.

In another embodiment, a method is provided that includes the steps of:

(a) a second switch/server receiving a request from a first subscriberto be associated with a second communication device controlled by thesecond switch/server, the first subscriber also being associated with afirst communication device controlled by a first switch/server differentfrom the second switch/server;

(b) the second switch/server notifying the first switch/server of therequest; and

(c) the second switch/server associating the second communication devicewith the first subscriber. The first subscriber is able to make outgoingcalls from and receive incoming calls at the second communication deviceand to access at least some features accessible by the first subscriberat the first communication device.

The present invention can have a number of advantages. It can allowsubscribers to roam in an enterprise network while still retaining atleast some of their home station capabilities. This provides a networkwide hot-desking capability. Second, it can provide service in a simpleand robust way with straightforward administration but not requiring newnetwork components/servers. This ease of incorporation into existingenterprise network architectures is made by possible by the softwareenablement of the mobility feature. It can enable balancing of callprocessing loads among multiple switches/servers.

A computer readable medium comprising processor executable instructionsto perform the steps of claim 1.

The present invention can provide a number of advantages depending onthe particular configuration.

These and other advantages will be apparent from the disclosure of theinvention(s) contained herein.

As used herein, “at least one”, “one or more”, and “and/or” areopen-ended expressions that are both conjunctive and disjunctive inoperation. For example, each of the expressions “at least one of A, Band C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “oneor more of A, B, or C” and “A, B, and/or C” means A alone, B alone, Calone, A and B together, A and C together, B and C together, or A, B andC together.

The above-described embodiments and configurations are neither completenor exhaustive. As will be appreciated, other embodiments of theinvention are possible utilizing, alone or in combination, one or moreof the features set forth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an architecture according to an embodimentof the present invention;

FIG. 2 is an inter-switch signal flow diagram according to an embodimentof the present invention; and

FIG. 3 is a flow chart according to an embodiment of the presentinvention.

DETAILED DESCRIPTION

According to a first embodiment of the present invention, first andsecond enterprise switch/servers 100 and 104 are interconnected by firstand second private and/or public networks 108 and 110. The terms“switch”, “server”, and “switch and/or server” as used herein should beunderstood to include a PBX, an ACD, an enterprise switch, an enterpriseserver, or other type of telecommunications system switch or server, aswell as other types of processor-based communication control devicessuch as media servers, computers, adjuncts, etc. Each of the first andsecond switch/server 100 and 104 services corresponding first and secondenterprise premises 112 and 116, respectively. In one configuration, thefirst network 108 is a circuit-switched network, such as the PublicSwitch Telephone Network or PSTN, while the second network 110 is apacket-switched network, such as the Internet. Each of the first andsecond switches is connected via a plurality of trunks 120 and 124,respectively, (which may be for example Primary Rate Interface, BasicRate Interface, Internet Protocol, and H.323 trunks) to the network 108and via link(s) 128 and 132, respectively, to the first, second, . . .Nth stations 136 a-n and first, second, . . . Mth stations 140 a-m,respectively. A gateway (not shown), such as Avaya Inc.'s, G700™, G650™,G600™, MCC/SCC™ media gateways, may be positioned logically between eachof the first and second switches/servers and the second network 110 toprocess communications passing between the appropriate switch/server andthe second network.

The stations, or communication devices, 136 a-n and 140 a-m arecircuit-switched and/or TDM devices. As will be appreciated, thestations 136 and 140 are normally plugged into a Tip ring interface thatcauses electronic signals from the station to be placed onto a TDM bus(not shown). Each of the stations corresponds to one of a set ofinternal (Direct-Inward-Dial) extensions on its controllingswitch/server. The controlling switch/server can direct incomingcontacts to and receive outgoing contacts from these extensions in aconventional manner. The stations 136 and 140 can include, for example,wired and wireless telephones, PDAs, H.320 video phones and conferencingunits, voice messaging and response units, and traditional computertelephony adjuncts. Examples of suitable devices are the 30010™, 2410™,and 2420™ Digital Telephones of Avaya, Inc.

Although not shown, each of the first and second premises 112 and 116can include packet-switched stations or communication devices, such asIP hardphones (e.g., Avaya Inc.'s 4600 Series IP Phones™), IP softphones(e.g., Avaya Inc.'s IP Softphone™), Personal Digital Assistants or PDAs,Personal Computers or PCs, laptops, packet-based H.320 video phones andconferencing units, packet-based voice messaging and response units, andpacket-based traditional computer telephony adjuncts. Examples ofsuitable devices are the 4610™, 4621 SW™, and 9620™ IP telephones ofAvaya, Inc.

It should be noted that the invention does not require any particulartype of information transport medium or protocol between switch/serverand stations and/or between the first and second switches/servers, i.e.,the invention may be implemented with any desired type of transportmedium as well as combinations of different types of transport media.For example, the inter-switch protocols may be QSIG, SIP, H.323, and thelike. Inter-agent 150 control signaling can be transmitted over thefirst and/or second network.

Each of the first and second switches/servers 100 and 104 are preferablysoftware-controlled and include a controlling application, such as amodified form of Communication Manager™ by Avaya, Inc. As can be seenfrom FIG. 1, the memory of each of the first and second switches/serversinclude a mobility agent 150 to provide mobility for wired subscriberstations. The mobility agents 150 provide the capability of subscribersto register as a remote user at premises controlled by a differentswitch/server than the premises of the subscriber's home station. Uponregistration, the mobility agent 150 of the home switch/server forwardsan image of the subscriber's home station to mobility agent 150 of thevisited, or remote, switch/server. The mobility agent 150 in the visitedswitch/server downloads the image to the visited station.

Incoming calls to the subscriber are routed to the visited station ofthe subscriber but most, if not all, of the functionality accessible tothe subscriber via his or her home station is retained in thesubscriber's home switch/server. Examples of such functionality includebridging (e.g., providing a bridged call appearance to permit anassistant bridge onto the subscriber's call), call coverage (e.g., callcoverage answer group), speed-dials, ringing patterns, customized textlabels, abbreviated dial lists, automatic message waiting, automaticdial (e.g., call back), automatic intercom, busy indication for anotherextension or trunk, call appearance, call forwarding, call forward(busy/do not answer), dial intercom, extension to cellular (discussedbelow), exclusion, personal Central Office or CO-line (per-CO-line),send all calls, hunt group or internal extension group, prioritycalling, and attendant calling. This list is an example of Avayafeatures and not exhaustive of the features that can be supported withthis approach. For outgoing calls, the subscriber's normal home(enterprise) identity (e.g., home telephone number) is sent as thecalling party information regardless of whether the call is processed atthe home or visited station. Where the call is processed at the visitedswitch/server and the first network 108 will not accept the subscriber'snormal calling party information (e.g., name and home station phonenumber), the subscriber's calling information for the visited station(e.g., name and visited station phone number) is sent as an option.Emergency (e.g., 911) calls are processed by sending only locallyapplicable calling party information to ensure that emergency responsepersonnel can respond correctly and effectively as well as call back ifthe need arises. For example, if the subscriber were to make anemergency call from the visited station, the visited switch/server wouldprovide to the Public Safety Access Point or PSAP the telephone numberand/or location information (e.g., Emergency Location Information Numberof ELIN) of the visited station not the subscriber's home station.

In the following paragraphs, the functionality of the architecture willbe discussed with reference to a specific example. In the example, afirst subscriber having, as his or her home station, the first station136 a controlled by the first switch/server 100 registers, as his or hervisited station, the second station 140 b controlled by the secondswitch/server 104. As discussed below, the first and second stations 136a and 140 b can be the same or different types of communication devices.In other words, they can have the same or different dial pad layout andbuttons, call appearances, programmable keys, and feature accessbuttons.

With this example in mind, the memories of the first and secondswitches/servers include a number of data structures to affect theforegoing functionality. The data structures include the home stationrecord 160 for the first station 136 a, the home application record 164for the first station 136 a, the native station record 168 for thesecond station 140 b, and the visitor application record 172 for thesecond station 140 b. The home station record 160 is the administeredrecord for the first station and includes a variety of information, suchas first subscriber's name (or UI), first subscriber public name, firststation private number (e.g., a five-digit internal extension), firststation public number (e.g., a 10-digit DID), first subscriber homesecurity information (e.g., a security code such as PIN), first stationtype, first station button/key record (which provides, for eachbutton/key the corresponding label or type and state), COS for the firststation, whether the first station is mobility enabled, call stateinformation (e.g., what call appearance is active, what call appearanceis ringing, and the like), and a pointer to the home application record(if not concatenated to the home station record for the first station).The home application record 164 includes the extension of the secondstation, second station type, a pointer to the home station record forthe first station (if not concatenated to the home station record forthe first station), and a pointer to the system being visited. Thenative station record 168 for the second station contains the same typesof information as the home station record for the first station, exceptthat the information corresponds to the second subscriber. The secondstation is the home station for the second subscriber. Finally, thevisitor application record 172 includes all information needed for thefirst subscriber to make a call from the second station 140 b. Ittherefore includes the first subscriber public name, first stationprivate number (e.g., a five-digit internal extension), first stationpublic number (e.g., a 10-digit DID), second station 140 b privatenumber, first subscriber home security information (e.g., a securitycode such as PIN), first and second station types, call stateinformation (e.g., what call appearance is active, what call appearanceis ringing, and the like), and second station button/key record havingbuttons/keys identical to those in the button/key record in the nativestation record 168. Preferably, the records 160, 164, 168, or 172 areobject-oriented, though they may be relational data structures.

The visitor application record 172 and native station record for thesecond station 168 are independent of one another; that is, they areseparate records, or located at physically distinct locations in memory,can both survive system resets, and generally do not point to orotherwise reference one another. This permits the second station to beused physically by the first (visiting) subscriber and logically by thesecond (native) subscriber. Stated another way, the native stationrecord is associated with a virtual (or Administration WithOut Hardwareor AWOH) station having the public and private numbers of the secondstation 140 b, while the visitor application record is associated withthe physical second station 140 b. Thus, the second station 140 beffectively has two identities, one is defined by the native stationrecord 168 and the other by the visitor application record 172. Inconventional mobility applications, the visited station loses theidentity of its native second subscriber, or the native station recordis replaced by the visitor application record 172.

The operation of the mobility agents 150 will now be described withreference to FIGS. 1-3.

The registration process commences in step 300 when the second station140 b receives from the first subscriber the feature access code of themobility agent 150, the home extension of the first station 136 a, andthe first subscriber's authentication information.

In response, the mobility agent 150 of the second switch/server 104sends, in step 304, a location update message 200 to the mobility agent150 in the first switch/server 100. The location update message 200includes the extension of the second station 140 b, the extension of thefirst station 136 a, the entered first subscriber's home securityinformation, and the second station's 140 station type. The locationupdate message 200 is effectively a registration request by the firstsubscriber to register for wired mobility from the first station 136 ato the second station 140 b.

In step 308, the mobility agent 150 of the first switch/server 100receives the location update message 200 and compares the home securityinformation in the home station record 160 against the entered homesecurity information. If the information fails to match or if the homestation record 160 indicates that the first station 136 a is noteligible for wired mobility (e.g., using the COS permissions), the agent150 denies the request and returns a denial message to the mobilityagent in the second switch/server. If the information matches and if thehome station record 160 indicates that the first station 136 a iseligible for wired mobility, the agent 150 proceeds to step 312. If thehome station record 160 indicated that the user is already associatedwith a different station, a deregistration indication will be passed tothe visited system for the previously visited station.

In step 312, the mobility agent 150 in the first switch/server 100creates a home application record 164 and a button map of the firststation 136 a. The button map can be any set of data structures definingthe layout of the keys and buttons of the first station 136 a. As willbe appreciated, there are two types of buttons/keys, namely statusbuttons (e.g., a button that indicates the state of and, when pressed,invokes a feature such as send all calls) and call origination buttons(e.g., speed or abbreviated dial). The button map typically indexesbutton/key identifiers against corresponding status and originationbutton/key types or labels (or first subscriber selected or programmedfunctions or features) and states. At least each programmable button/keyon the first station 136 a, and in some applications nonprogrammablebuttons/keys, has a corresponding button identifier. In other words, themap has, for each button/key identifier, a corresponding button/key typeor label and button/key state. For example, the button map includesabbreviated dial buttons, intercom buttons, and bridged appearances ofother extensions on the first station 136 a. “Button” and “key” are usedherein as alternate expressions for signal activators.

In step 316, the mobility agent 150 in the first switch/server 100 sendsa location response 204 to the mobility agent 150 in the secondswitch/server 104. When the first and second stations are of the sametype, the response 204 includes the first station type, button map,message waiting state indicator, first subscriber's public number, firstsubscriber's private number, and the first subscriber's public name.When the first and second stations are of different types, the response204 may optionally include the second station's private number, thesecond station's public number, and the definition for the callappearances of the first station 136 a for mapping to the visited set.

In step 320, the mobility agent 150 in the second switch/server 104receives the awaited response 204 and creates the visitor applicationrecord 172. The second station button/key record is produced by themobility agent 150 in the second switch/server 104 by mapping the buttonmap of the first station 136 a against the button/key layout of thesecond station 136 b. When the first and second stations are of the sametype, the home station record 160 and visitor application record 172 aresubstantially the same, though the layouts of the records differ. Whenthe first subscriber activates buttons/keys on the second station 140 b,the application record 172, and not the home station record 160, is usedto determine the corresponding function.

In step 324, the mobility agent 150 in the second switch/server 104reconfigures the second station 140 b as defined in the visitorapplication record 172. When the first and second stations 136 a and 140b are of different types only a default set of features are provided onthe second station or, alternatively, matching keys/buttons are givencommon functionality. When the first and second stations 136 a and 140 bare of the same type, the stations appear to be the same to the firstsubscriber. The first station 136 a, during the duration of mobilityregistration, displays that mobility registration is in effect andprovides the private number of the second station 140 b

Deregistration is effected by the first subscriber entering a deactivatefeature access code, the private extension of the first station 136 a,and the security information. A deregistration message 220 containingthis information is then sent from the second switch/server 104 to themobility agent 150 at the first switch/server. After successfulauthentication, the registration is cleared at the first switch/server100 and a response is returned to the mobility agent 150 in the secondswitch/server 104. In that event, the home and visitor applicationrecords 164 and 172 are cleared from memory. Deregistration can also beeffected automatically by the expiration of an automatic deregistrationtimer or placement of an emergency call from the second station 140 b.Deregistration may also be initiated at the first switch/server 100 bythe first subscriber entering the deregistration information notedpreviously or automatically in the response of a successful registrationof the user on another station.

Preferably, the messages 200, 204, 208, 212, 216, and 220 are sentout-of-band (e.g., over the D-channel in the QSIG protocol) relative tothe voice channel to conserve bandwidth.

When there is an incoming call to the first station 136 a while thefirst subscriber is mobility registered at the second station 140 b, themobility agent 150 in the first switch/server 100 determines from theapplication record 164 that mobility registration is in effect and thatthe first subscriber is registered at the second station 140 b. The callsetup message is forwarded to the mobility agent 150 in the secondswitch/server 104 to set up the call. When there is an incoming call tothe second station 140 b that is not routed via the first switch/server100 while the first subscriber is mobility registered at the secondstation 140 b, the mobility agent 150 in the second switch/server 104determines from native station record 168 the proper treatment of thecall, which includes directing the call to call coverage for the secondsubscriber. In this manner, the second subscriber can receive calls tothe public and private numbers of the second station, make callsremotely that are associated with the second station, and accessfeatures remotely using feature access codes even while mobilityregistration is in effect for the first subscriber.

When, during mobility registration, the first switch/server receives anincoming call to the first subscriber, the mobility agent 150 in thefirst switch/server 100 generates and sends an appearance update message216. The message 216 contains the first subscriber's private number forthe first station 136 a, the private number for the second station 140b, an identifier of the incoming call, and the call appearance selectedfor the incoming call. This can be important because the first andsecond switches/servers can be configured to select call appearancesdifferently. By including the call appearance in the message 216, thesame call appearance is used for the first and second stations 136 a and140 b to identify the incoming call. The receipt of the update message216 informs the second switch/server that the incoming call is for thefirst and not the second subscriber and therefore the mobility agent 150in the second switch/server 104 uses the visitor application record 172and not the native station record 168 to process the incoming call.

It is important to note that the second station 140 b is tied to thevisitor application record 172 during mobility registration and not thenative station record 168. Thus, if an incoming call to the firstsubscriber is rung the second station 140 b will be rung. However, if anincoming call to the second subscriber is rung the second station 140 bwill not be rung.

Incoming calls to the first subscriber while mobility registered at thesecond station are normally controlled by the first switch/server 100and not the second switch/server 104. Home switch/server control of thecall is preferably used so that call processing for call coverage ordiversion into voice messaging is managed at the first switch/server100. Using the first switch/server 100 to process incoming calls causesa first call to be set up between the calling party and the firstswitch/server and a second call to be set up between the first andsecond switches/servers. When all or part of the call processing is doneby the second switch/server 104, the call will still be accessible atthe first station or bridged appearances of that extension unless pathreplacement were to occur. Outgoing calls made using the dial pad on thesecond station 140 b are processed by the second switch/server 104.However, call origination features accessed by the first subscriber atthe second station 140 b are normally processed at the firstswitch/server 100. For example when using a bridged appearance button, acall is set up to the first switch/server 100, and any call initiatedusing the dial pad of the second station 140 b is processed by the firstswitch/server 100. Calls using an abbreviated dial or intercom featurebutton on the second station 140 b to place the call are processed bythe first switch/server 100 using the number stored in the abbreviateddial list on the first switch/server. This is preferable because dialstring variances used in different locales to reach the same destinationwould be normal in different switches in a network. Even Automatic RouteSelection or ARS access codes may vary by country due to local dialingcustoms. Using the first switch/server 100 to process such calls causesa first call to be set up between the first and second switches/serversand a second call to be set up between the first switch/server and thecalled destination. When making an outgoing call from the second station140 b, the mobility agent 150 in the second switch/server 104 sends anappearance update message 218 to the mobility agent 150 in the firstswitch/server providing the call appearance selected for the secondstation 140 b for the call. In this way, the call appearances selectedfor the first and second stations 136 a and 140 b for the outgoing callare the same and conflicts in which the same call appearance is selectedfor different calls are avoided.

Button status update messages 208 and 212 are used for the continuousupdate of buttons that are tracked (e.g., call appearances and bridgedappearances). When an update message is received by a mobility agent150, the agent updates the host (e.g., first or second) switch/server'sbutton/key record for the controlled station (e.g., the first or secondstation). Available update messages 208 and 212 include idle, alertingwith and without ringing and in-use states. The stimulus for suchmessages is the activation of button/key of the first or second station,as appropriate. Thus, when a feature button is pressed at the secondswitch/server 104, the mobility agent 150 in the second switch/serversends an update message 212 to the first switch/server so the desiredfeature is activated or deactivated. When a button status at the firststation 136 a changes, the mobility agent 150 in the first switch/server100 sends an update message 208 so the second station can be updated.When calls are launched by button origination (i.e., abbreviated dial)from the second switch/server to the first switch/server, status updatesfor the call appearance are included in the setup and not sent inseparate messages.

Status buttons/keys are thus processed by the first switch/server 100.When a status button/key is pressed in the second station 140 b, abutton status update message 212 is sent by the mobility agent 150 inthe second switch/server 104 to the mobility agent 150 in the firstswitch/server 100. The feature is then activated in the firstswitch/server 100. This home switch feature processing is done to save aphone call. For example, when the pressed status button/key is “send allcalls” the first switch/server 100 and not the second switch/server 104knows how to route the extension.

Although not depicted in FIG. 2, message waiting update messages areused to notify the second switch/server 104 of the first subscriber'smessage waiting lamp status and update that status whenever it changes.

A number of variations and modifications of the invention can be used.It would be possible to provide for some features of the inventionwithout providing others.

For example in one alternative embodiment, the above functionality isapplied to packet-switched communications. The various messages and datastructures noted above are used except that the messages are packetizedand transmitted over the second network 110, which is the same networkused by the voice bearer channel.

In another alternative embodiment, the concepts of the invention areapplied to enable intra-switch/server mobility. In this embodiment, thehome and visited stations are controlled by a common switch/server. Forexample, the first or home station 136 a and a second or visited station136 b are controlled by the first switch/server 100. To enablesubscriber mobility on the premises 100, the home station record 160 forthe first station 136 a, home application record 164 for the firststation 136 a, native station record 168 for the second station 136 b,and visitor application record 172 for the second station 136 b are alllocated in the memory of the first switch/server 100.

In yet another embodiment, a feature accessible from the remote orvisited station is Off Premises Telephony Integration Mobility or OPTIM.This feature allows the first subscriber to receive an incoming call oneither his cellular phone or wired station and easily transfer ananswered call from his cellular phone to the wired station by simplypressing a button (such as a call appearance button) on the wiredstation. Alternatively, the subscriber can transfer an answered callfrom the wired station to the cellular phone by pressing a featurebutton on the wired station, which initiates a call to the cellularphone. Additionally, a call from the cellular phone appears to thecallee to be a local call from the wired station.

In yet another embodiment, dedicated hardware implementations including,but not limited to, Application Specific Integrated Circuits or ASICs,programmable logic arrays, and other hardware devices can likewise beconstructed to implement the methods described herein. Furthermore,alternative software implementations including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein.

It should also be stated that the software implementations of thepresent invention are optionally stored on a tangible storage medium,such as a magnetic medium like a disk or tape, a magneto-optical oroptical medium like a disk, or a solid state medium like a memory cardor other package that houses one or more read-only (non-volatile)memories. A digital file attachment to e-mail or other self-containedinformation archive or set of archives is considered a distributionmedium equivalent to a tangible storage medium. Accordingly, theinvention is considered to include a tangible storage medium ordistribution medium and prior art-recognized equivalents and successormedia, in which the software implementations of the present inventionare stored.

Although the present invention describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the invention is not limited to such standards andprotocols. Other similar standards and protocols not mentioned hereinare in existence and are considered to be included in the presentinvention. Moreover, the standards and protocols mentioned herein andother similar standards and protocols not mentioned herein areperiodically superseded by faster or more effective equivalents havingessentially the same functions. Such replacement standards and protocolshaving the same functions are considered equivalents included in thepresent invention.

The present invention, in various embodiments, includes components,methods, processes, systems and/or apparatus substantially as depictedand described herein, including various embodiments, subcombinations,and subsets thereof. Those of skill in the art will understand how tomake and use the present invention after understanding the presentdisclosure. The present invention, in various embodiments, includesproviding devices and processes in the absence of items not depictedand/or described herein or in various embodiments hereof, including inthe absence of such items as may have been used in previous devices orprocesses, e.g., for improving performance, achieving ease and\orreducing cost of implementation.

The foregoing discussion of the invention has been presented forpurposes of illustration and description. The foregoing is not intendedto limit the invention to the form or forms disclosed herein. In theforegoing Detailed Description for example, various features of theinvention are grouped together in one or more embodiments for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimed inventionrequires more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive aspects lie in less than allfeatures of a single foregoing disclosed embodiment. Thus, the followingclaims are hereby incorporated into this Detailed Description, with eachclaim standing on its own as a separate preferred embodiment of theinvention.

Moreover, though the description of the invention has includeddescription of one or more embodiments and certain variations andmodifications, other variations and modifications are within the scopeof the invention, e.g., as may be within the skill and knowledge ofthose in the art, after understanding the present disclosure. It isintended to obtain rights which include alternative embodiments to theextent permitted, including alternate, interchangeable and/or equivalentstructures, functions, ranges or steps to those claimed, whether or notsuch alternate, interchangeable and/or equivalent structures, functions,ranges or steps are disclosed herein, and without intending to publiclydedicate any patentable subject matter.

1. A method, comprising: (a) receiving, by a second switch/server, arequest from a first subscriber to be associated with a secondcommunication device controlled by the second switch/server, wherein thefirst subscriber is also associated with a first communication devicecontrolled by a first switch/server different from the secondswitch/server; (b) notifying, by the second switch/server, the firstswitch/server of the request; and (c) associating, by the secondswitch/server, the second communication device with the firstsubscriber, whereby the first subscriber is able to make outgoing callsfrom and receive incoming calls at the second communication device andto access at least some features accessible by the first subscriber atthe first communication device, wherein an image of the firstcommunication device is downloaded, via the switches, to the secondcommunication device, wherein the association is ended by aderegistration process that is effected by one or more of: an automaticexpiration of the registration, an emergency call from the secondcommunication device, and the first subscriber entering deregistrationinformation in response to a successful registration of the user onanother station, all of which cause the association be cleared from thefirst switch/server and a visitor application record from the secondswitch/server.
 2. The method of claim 1, wherein the secondcommunication device is normally associated with a second subscriber,wherein the request notification in step (b) comprises a number of thesecond communication device, a number of the first communication device,and the first communication device type and wherein the associating step(c) comprises the substeps: (c1) the first switch/server creating a homeapplication record and a button map of the first communication device;(c2) the first switch/server forwarding the first communication devicetype, button map, message waiting state indicator, first communicationdevice number, and first subscriber's name to the second switch/server;(c3) using information received in substep (c2), the secondswitch/server creating a visitor application record associating thefirst subscriber with the second communication device; and (c4) thesecond switch/server reconfiguring the second communication device asdefined in the visitor application record.
 3. The method of claim 1,wherein the second communication device is normally associated with asecond subscriber, wherein the second switch/server comprises a nativecommunication device record for the second communication device, whereinthe first switch/server comprises a visitor application record for thesecond communication device, wherein the native communication devicerecord is associated with the second subscriber, and the visitorapplication record is associated with the first subscriber, wherein thenative communication device record is, while the first subscriber isassociated with the second communication device, associated with avirtual communication device, and wherein the virtual communicationdevice and second communication device have a common number.
 4. Themethod of claim 3, wherein the first switch/server comprises a homecommunication device record for the first communication device, the homecommunication device record configuring the first communication devicefor the first subscriber and a home application record to redirectincoming calls for the first communication device to the secondcommunication device, wherein the first and second communication devicesare at least one of circuit-switched and time division multiplexed,wherein at least most of the following features are available to thefirst subscriber while the first subscriber is associated with thesecond communication device: bridging an incoming call to the firstsubscriber onto the first communication device, call coverage,speed-dialing, ringing patterns, customized button labels, abbreviateddial list, automatic call back, automatic message waiting, automaticintercom, busy indication for another extension or trunk, callappearance, call forwarding, call forward (busy/do not answer), dialintercom, extension to cellular, exclusion, personal CentralOffice-line, send all calls, internal extension group, priority calling,and attendant calling, wherein, for outgoing calls from the secondsubscriber device, a number of the first communication device is sent ascalling party information while the first subscriber is associated withthe second communication device, and wherein, when an outgoing call to auniversal emergency number is made from the second communication device,the first subscriber is disassociated automatically with the secondcommunication device.
 5. The method of claim 4, wherein the visitorapplication record comprises at least the following information: thefirst subscriber's name, the first communication device's number, thesecond communication device's number, the first subscriber's homesecurity information, the first and second communication device types,call state information, and a second communication device button recordhaving a set of a plurality of buttons identical to a set of a pluralityof buttons on the first communication device and wherein the nativecommunication device record comprises at least the followinginformation: second subscriber's name, second communication device'sprivate number, second communication device's public number, secondsubscriber's home security information, second communication devicetype, second communication device's button record configured for thesecond subscriber, class of service for the second communication device,and call state information, wherein the home communication recordcomprises at least the following information: first subscriber's name,first communication device's private number, first communicationdevice's public number, first subscriber's home security information,first communication device type, first communication device buttonrecord configured for the first subscriber, class of service for thefirst communication device, and call state information and wherein thehome application record comprises at least the following information:the number of the second communication device and the secondcommunication device type, a pointer to the home station record for thefirst station, and wherein the home communication device record and homeapplication record are associated with one another.
 6. The method ofclaim 1, wherein, while the first subscriber is associated with thesecond communication device, incoming calls to the second subscriber areprocessed as defined in the native communication device record and notdirected to the second communication device, and incoming calls to thefirst subscriber are directed by the first switch/server to the secondswitch/server and by the second switch/server to the secondcommunication device, and outgoing calls from the first subscriberinitiated using the second communication device are directed by thesecond switch/server to the first switch/server setup with calleddestination.
 7. The method of claim 6, wherein, when an incoming call isdirected by the first switch/server to the second switch/server, thefirst switch/server sends to the second switch/server a call appearanceselected for the call and wherein, when an outgoing call is directed bythe second switch/server to the first switch/server, the secondswitch/server sends to the first switch/server a call appearanceselected for the call.
 8. A tangible computer readable medium comprisingprocessor executable instructions that, when executed, perform the stepsof claim
 1. 9. A system, comprising: (a) a second switch/server operableto receive a request from a first subscriber to be associated with asecond communication device controlled by the second switch/server,wherein the first subscriber is also associated with a firstcommunication device controlled by a first switch/server different fromthe second switch/server; (b) the second switch/server operable tonotify the first switch/server of the request; and (c) the secondswitch/server operable to associate the second communication device withthe first subscriber, whereby the first subscriber is able to makeoutgoing calls from and receive incoming calls at the secondcommunication device and to access at least some features accessible bythe first subscriber at the first communication device, wherein an imageof the first communication device is downloaded, via the switches, tothe second communication device wherein the association is ended by aderegistration process that is effected by one or more of: an automaticexpiration of the registration, an emergency call from the secondcommunication device, and the first subscriber entering deregistrationinformation in response to a successful registration of the user onanother station, all of which cause the association be cleared from thefirst switch/server and a visitor application record from the secondswitch/server.
 10. The system of claim 9, wherein the secondcommunication device is normally associated with a second subscriber,wherein the request notification in step (b) comprises a number of thesecond communication device, a number of the first communication device,and the first communication device type and wherein the associating step(c) comprises the substeps: (c1) the first switch/server creating a homeapplication record and a button map of the first communication device;(c2) the first switch/server forwarding the first communication devicetype, button map, message waiting state indicator, first communicationdevice number, and first subscriber's name to the second switch/server;(c3) using information received in substep (c2), the secondswitch/server creating a visitor application record associating thefirst subscriber with the second communication device; and (c4) thesecond switch/server reconfiguring the second communication device asdefined in the visitor application record.
 11. The system of claim 9,wherein the second communication device is normally associated with asecond subscriber, wherein the second switch/server comprises a nativecommunication device record for the second communication device, whereinthe first switch/server comprises a visitor application record for thesecond communication device, wherein the native communication devicerecord is associated with the second subscriber, and the visitorapplication record is associated with the first subscriber, wherein thenative communication device record is, while the first subscriber isassociated with the second communication device, associated with avirtual communication device, and wherein the virtual communicationdevice and second communication device have a common number.
 12. Thesystem of claim 11, wherein the first switch/server comprises a homecommunication device record for the first communication device, the homecommunication device record configuring the first communication devicefor the first subscriber and a home application record to redirectincoming calls for the first communication device to the secondcommunication device, wherein the first and second communication devicesare at least one of circuit-switched and time division multiplexed,wherein at least most of the following features are available to thefirst subscriber while the first subscriber is associated with thesecond communication device: bridging an incoming call to the firstsubscriber onto the first communication device, call coverage,speed-dialing, ringing patterns, customized button labels, abbreviateddial list, automatic call back, automatic message waiting, automaticintercom, busy indication for another extension or trunk, callappearance, call forwarding, call forward (busy/do not answer), dialintercom, extension to cellular, exclusion, personal CentralOffice-line, send all calls, internal extension group, priority calling,and attendant calling, wherein, for outgoing calls from the secondsubscriber device, a number of the first communication device is sent ascalling party information while the first subscriber is associated withthe second communication device, and wherein, when an outgoing call to auniversal emergency number is made from the second communication device,the first subscriber is disassociated automatically with the secondcommunication device.
 13. The system of claim 12, wherein the visitorapplication record comprises at least the following information: thefirst subscriber's name, the first communication device's number, thesecond communication device's number, the first subscriber's homesecurity information, the first and second communication device types,call state information, and a second communication device button recordhaving a set of a plurality of buttons identical to a set of a pluralityof buttons on the first communication device and wherein the nativecommunication device record comprises at least the followinginformation: second subscriber's name, second communication device'sprivate number, second communication device's public number, secondsubscriber's home security information, second communication devicetype, second communication device's button record configured for thesecond subscriber, class of service for the second communication device,and call state information, wherein the home communication recordcomprises at least the following information: first subscriber's name,first communication device's private number, first communicationdevice's public number, first subscriber's home security information,first communication device type, first communication device buttonrecord configured for the first subscriber, class of service for thefirst communication device, and call state information and wherein thehome application record comprises at least the following information:the number of the second communication device and the secondcommunication device type, a pointer to the home station record for thefirst station, and wherein the home communication device record and homeapplication record are associated with one another.
 14. The system ofclaim 9, wherein, while the first subscriber is associated with thesecond communication device, incoming calls to the second subscriber areprocessed as defined in the native communication device record and notdirected to the second communication device, and incoming calls to thefirst subscriber are directed by the first switch/server to the secondswitch/server and by the second switch/server to the secondcommunication device, and outgoing calls from the first subscriberinitiated using the second communication device are directed by thesecond switch/server to the first switch/server setup with calleddestination.
 15. The system of claim 14, wherein, when an incoming callis directed by the first switch/server to the second switch/server, thefirst switch/server sends to the second switch/server a call appearanceselected for the call and wherein, when an outgoing call is directed bythe second switch/server to the first switch/server, the secondswitch/server sends to the first switch/server a call appearanceselected for the call.